This is a question for you to answer. ColdBox supports the mode of being in debug mode or not. It does so, by placing a cookie on your browser so you can see the debugging panel only with that cookie set. The question is, how long should that cookie live? What should the expiration time be? Any suggestions?
Blog
Recent Entries
![Ortus June 2024 Newsletter!](/__media/contentbox:2024/banners/Ortus-Newsletter-June.png)
Ortus June 2024 Newsletter!
Welcome to the latest edition of the Ortus Newsletter! This month, we're excited to bring you highlights from our sessions at CFCamp and Open South Code, as well as a sneak peek into our upcoming events. Discover the latest developments in BoxLang, our dynamic new JVM language, and catch up on all the insightful presentations by our expert team. Let's dive in!
![BoxLang June 2024 Newsletter!](/__media/contentbox:2024/banners/BoxLang-June-Newsletter.png)
BoxLang June 2024 Newsletter!
We're thrilled to bring you the latest updates and exciting developments from the world of BoxLang. This month, we're diving into the newest beta release, introducing a new podcast series, showcasing innovative integrations, and sharing insights from recent events. Whether you're a seasoned developer or just getting started, there's something here for everyone to explore and enjoy.
![BoxLang 1.0.0 Beta 3 Launched](/__media/contentbox:2024/boxlang/boxlang-1.0.0-beta3.png)
BoxLang 1.0.0 Beta 3 Launched
We are thrilled to announce the release of BoxLang 1.0.0-Beta 3! This latest beta version is packed with exciting new features and essential bug fixes, including robust encryption functionality, enhanced Java interoperability, and more efficient event handling. Key highlights include the introduction of query caching capabilities, seamless coercion of Java Single Abstract Method (SAM) interfaces from BoxLang functions, and support for virtual thread executors. So, let’s dive into the details of what’s new in BoxLang 1.0.0-Beta 3 and how you can start leveraging these updates today!
Add Your Comment
(4)
Feb 23, 2007 03:50:04 UTC
by Sana
Hi Luis, I think 30 minutes, as sessions default expiry is 30 minutes, so this cookie should be 30 minutes expiry time.
Feb 23, 2007 07:29:14 UTC
by Dan Wilson
Luis, Perhaps it could be left up to the user to clear the cookie when they have finished the debugging? A link or a special URL perhaps to clear the cookie? Dan
Feb 23, 2007 10:00:43 UTC
by reuben
I agree with Sana that the time out for a cookie should be defaulted to the session timeout. If you are working constantly on the site, the debug will last beyond 30 minutes. The big issue is that if you stop work and come back to the site, you don't always want debug still enabled. I think having it auto expire is a good thing.
Feb 23, 2007 10:24:47 UTC
by Luis Majano
Dan, You can clear the cookie by just setting debugmode=false once you are done. But we all know that sometimes we are lazy and basically forget, like 90 year old brians!! So an automatic timeout, would allow security and also peace of mind. I think 30 minutes is reasonable. Any more suggestions.